Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

docs/docs/administration/08-advanced/06-migrate-greenlight.md (1)

6-6: Tighten the updated prose.

A few changed sentences have small grammar/readability issues.

📝 Proposed wording cleanup

-PILOS provides an easy to use command to import all Greenlight users (incl. ldap), rooms (incl. default presentation) and shared accesses.
+PILOS provides an easy-to-use command to import all Greenlight users (incl. LDAP), rooms (incl. default presentation) and shared accesses.

-The command will output the process of the import and informs about failed user, room, room presentation and shared access import.
+The command will show the import progress and report failed user, room, room presentation and shared access imports.

-This meeting does not have a start- or end timestamp, so it not visible in the frontend. Associated recordings *will* be listed, however.
+This meeting does not have a start or end timestamp, so it is not visible in the frontend. Associated recordings *will* be listed, however.

Also applies to: 34-34, 140-141

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/docs/administration/08-advanced/06-migrate-greenlight.md` at line 6, The
sentence "PILOS provides an easy to use command to import all Greenlight users
(incl. ldap), rooms (incl. default presentation) and shared accesses." has
grammar and clarity issues—replace it with a tighter, more readable version such
as: "PILOS provides an easy-to-use command to import all Greenlight users
(including LDAP), rooms (including the default presentation), and shared
accesses." Update the same style in the other occurrences referenced (lines
containing similar phrasing at 34 and 140–141) to ensure consistent hyphenation,
expanded acronyms, and parallel list structure.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

docs/docs/administration/08-advanced/06-migrate-greenlight.md (1)

138-141: ⚠️ Potential issue | 🟡 Minor

Clarify that Meetings are created only for newly imported rooms.

Line 140 states the command creates a Meeting "for every imported room", but the importer skips room-id collisions and creates Meeting records only when creating new rooms. Users importing recordings for pre-existing/skipped rooms must create or verify the Meeting association themselves before importing recordings.

Additionally, "existing rooms" in line 140 is ambiguous—it could mean rooms that pre-existed in PILOS or rooms from Greenlight.

📝 Proposed documentation fix

-You can also import recordings for existing rooms. To make this possible the import command creates a meeting with the BBB meeting ID for every imported room.
+You can also import recordings for rooms imported by this command. For each newly imported room, the import command creates a meeting with the BBB meeting ID.
+If a room already existed in PILOS and was skipped by the import, create or verify the corresponding meeting association before importing recordings.
 This meeting does not have a start- or end timestamp, so it not visible in the frontend. Associated recordings _will_ be listed, however.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/docs/administration/08-advanced/06-migrate-greenlight.md` around lines
138 - 141, Update the paragraph about importing recordings to clarify that the
importer creates a Meeting record only when it creates a new Room (it skips on
room-id collisions), so it does not create Meetings for pre-existing rooms;
replace the ambiguous phrase "existing rooms" with explicit wording
distinguishing "rooms that already exist in your PILOS database" versus "rooms
from Greenlight", and add a short note that users importing recordings for
pre-existing/skipped rooms must manually create or verify the Meeting
association before importing recordings (refer to the importer/Meeting behavior
and room-id collision handling).

docs/docs/administration/08-advanced/06-migrate-greenlight.md (1)

145-145: Clarify that rooms table refers to the Greenlight database.

Step 1 instructs users to find the meeting ID in the rooms table, but doesn't specify whether this is the Greenlight or PILOS database. Users should query the Greenlight database.

📝 Proposed clarification

-1. find the meeting ID (column `bbb_id` (GL2) or `meeting_id` (GL3) in the `rooms` table)
+1. find the meeting ID (column `bbb_id` (GL2) or `meeting_id` (GL3) in Greenlight's `rooms` table)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/docs/administration/08-advanced/06-migrate-greenlight.md` at line 145,
Clarify that the "rooms" table referenced in step 1 is in the Greenlight
database by updating the sentence to read something like: "find the meeting ID
in the Greenlight app database (the rooms table — column `bbb_id` for GL2 or
`meeting_id` for GL3)"; ensure the mention of `rooms`, `bbb_id`, `meeting_id`,
and GL2/GL3 stays intact so readers know which database and columns to query.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes